<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en" xml:lang="en" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Work Product (Artifact): System-WideRequirements</title>
<meta name="uma.type" content="WorkProductDescriptor">
<meta name="uma.name" content="system_wide_requirements">
<meta name="uma.presentationName" content="System-WideRequirements">
<meta name="element_type" content="WorkProductDescriptor">
<meta name="filetype" content="description">
<meta name="role" content="">
<link rel="StyleSheet" href="./../../css/default.css" type="text/css">
<script src="./../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ActivityTreeTable.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ProcessElementPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/processElementData.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					var defaultQueryStr = '?proc=_RQi0AdONEdyqlogshP8l4g&path=_RQi0AdONEdyqlogshP8l4g,_AP_nodOOEdyqlogshP8l4g,_AQJYp9OOEdyqlogshP8l4g';
					var backPath = './../../';
					var imgPath = './../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, false, true, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td valign="top"><a name="Top"></a>
<div id="page-guid" value="_AQJYp9OOEdyqlogshP8l4g"></div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="pageTitle" nowrap="true">Work Product (Artifact): System-WideRequirements</td><td width="100%">
<div align="right" id="contentPageToolbar"></div>
</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../scripts/treebrowser.js"></script></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="pageTitleSeparator"><img src="./../../images/shim.gif" alt="" title="" height="1"></td>
</tr>
</table>
<div class="overview">
<table width="97%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50"><img src="./../../images/workdes_lg_dgm32.gif" alt="" title=""></td><td>
<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="top">This artifact captures the quality attributes and constraints that have system-wide scope. It also captures system-wide functional requirements.</td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Purpose</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td class="sectionTableSingleCell"><p> 
   This artifact is used for the following purposes: </p> <ul>
<li>         To describe the quality attributes of the system, and the constraints
that the design options must satisfy to deliver the business goals, objectives,
or capabilities     </li>
<li>         To capture functional requirements that are not expressed as
use cases     </li>
<li>         To negotiate between, and select from, competing design options
   </li>
<li>         To assess the sizing, cost, and viability of the proposed system
    </li>
<li>         To understand the service-level requirements for operational
management of the solution     </li>
</ul></td>
</tr>
</table>
</div>
<div class="sectionHeading">Relationships</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Fulfilled Slots</th><td class="sectionTableCell" colspan="2">
<ul>
<li>
<a href="./../../process.openup.base/capabilitypatterns/technical_specification_slot_6B2E9CEB.html" guid="_AVhA09OOEdyqlogshP8l4g">[Technical Specification]</a>
</li>
</ul>
</td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Roles</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Responsible:
								</span>
<ul>
<li>
<a href="./../../process.openup.base/capabilitypatterns/analyst_3BA2CC28.html" guid="_AQJYodOOEdyqlogshP8l4g">Analyst</a>
</li>
</ul>
</td><td class="sectionTableCell" colspan="2"><span class="sectionTableCellHeading">Modified By:
								</span>
<ul>
<li>
<a href="./../../process.openup.base/capabilitypatterns/analyst_3BA2CC28.html" guid="_AQJYodOOEdyqlogshP8l4g">Analyst</a>
</li>
</ul>
</td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Input To</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Mandatory:
								</span>
<ul>
<li>
<a href="./../../process.openup.base/capabilitypatterns/detail_system_wide_requirements_F7B6E716.html" guid="_AVhA0dOOEdyqlogshP8l4g">Detail System-Wide Requirements</a>
</li>
<li>
<a href="./../../process.openup.base/capabilitypatterns/create_test_cases_254C726.html" guid="_AVhA0tOOEdyqlogshP8l4g">Create Test Cases</a>
</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Optional:
								</span>
<ul>
<li>
<a href="./../../process.openup.base/capabilitypatterns/identify_and_outline_requirements_4D09B812.html" guid="_AQJYoNOOEdyqlogshP8l4g">Identify and Outline Requirements</a>
</li>
</ul>
</td><td class="sectionTableCell"><span class="sectionTableCellHeading">External:
								</span>
<ul>
<li>None</li>
</ul>
</td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Output From</th><td class="sectionTableCell" colspan="3">
<ul>
<li>
<a href="./../../process.openup.base/capabilitypatterns/detail_system_wide_requirements_F7B6E716.html" guid="_AVhA0dOOEdyqlogshP8l4g">Detail System-Wide Requirements</a>
</li>
<li>
<a href="./../../process.openup.base/capabilitypatterns/identify_and_outline_requirements_4D09B812.html" guid="_AQJYoNOOEdyqlogshP8l4g">Identify and Outline Requirements</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Description</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Brief Outline</th><td class="sectionTableCell"><p> Organize
system-wide requirements by a number of common themes or subcategories: the
areas of performance and capacity, availability, usability, security and privacy,
maintainability, manageability, and flexibility. See the supporting guidance
for a description of the recommended categorization approach. </p> <p>For
each system-wide requirement, capture attributes such as the source and priority
of the requirements, as described by the associated requirements management
guidance. </p></td>
</tr>
</table>
</div>
<div class="sectionHeading">Properties</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Optional" abbr="Optional">Optional</th><td class="sectionTableCell" align="left" headers="property_Optional"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Planned" abbr="Planned">Planned</th><td class="sectionTableCell" align="left" headers="property_Planned"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
</table>
</div>
<div class="sectionHeading">Illustrations	</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Templates</th><td class="sectionTableCell">
<ul>
<li>
<a href="./../../core.tech.common.extend_supp/guidances/templates/systemwide_requirements_specification_B621CDD6.html" guid="_m7p-AI5fEdyO5aWob1UGDA">System-Wide Requirements Specification</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Key Considerations</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td class="sectionTableSingleCell"><ul>
<li>         When you document system-wide requirements, ensure that the needs
of all of the stakeholders are represented. In         particular, include
the needs of those who are responsible for maintaining or supporting the system
after it is delivered.     </li>
<li>         Typically, there are some overlaps and gray areas between system-wide
requirements and other requirements work         products. For example, the
authorization behavior of a system can be specified as use cases or as statements
within system-wide requirements. The overall driving need is that no important
requirements are missed or duplicated, and that there is an agreed upon approach
for capturing and processing every type of requirement.     </li>
<li>         System-wide requirements originate from many places. Documenting
the source of the requirement is particularly         important when you separate
externally mandated requirements.     </li>
<li>         Requirements are often thought of as "Qualitative" (specifying
a quality or desirable characteristic) versus         "Quantitative" (specifying
a quantity). Qualitative requirements can sometimes be elaborated into quantitative
requirements.     </li>
<li>         A good quality requirement is one that you can verify, either
through testing or some other objective evaluation.     </li>
<li>         You must evaluate system-wide requirements for cost, schedule
impact, and level of contribution to business goals.         Based on your
evaluation, the system-wide requirements should be iteratively challenged,
defended, and amended.     </li>
</ul></td>
</tr>
</table>
</div>
<div class="sectionHeading">Tailoring</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Impact of not having</th><td class="sectionTableCell"><p> If
you do not adequately manage and meet system-wide requirements, you risk delivering
a system that might be unacceptable to stakeholders.<br/> </p></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Reasons for not needing</th><td class="sectionTableCell"><p >  You do not need to use this artifact if none of the categories of system-wide
requirements apply to the project under consideration. </p></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Representation Options</th><td class="sectionTableCell">This
artifact represents the influences on the design and delivery of a system,
which cover a broad range of themes. Document the requirements for each theme
under separate headings within a document or under appropriate category identifiers
in a requirements gathering tool. Give categories easy-to-recognize identifiers,
so individual requirements can be readily associated with the appropriate
category. The format of requirements vary from category to category; some
are heavily textual, and others are more structured and quantitative.</td>
</tr>
</table>
</div>
<div class="sectionHeading">More Information</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Guidelines</th><td class="sectionTableCell">
<ul>
<li>
<a href="./../../core.tech.common.extend_supp/guidances/guidelines/writing_good_requirements_48248536.html" guid="_6jXzYNcKEdqz_d2XWoVt6Q">Writing Requirements Statements</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<table class="copyright" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="copyright"><p> This program and the accompanying materials are made available under the<br />
  <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse 
  Public License V1.0</a>, which accompanies this distribution. </p><p/><p> <a class="elementLink" href="./../../core.default.release_copyright.base/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a></p></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script language="JavaScript" type="text/javascript">
					contentPage.onload();
					contentPage.processPage.fixDescriptorLinks();
				</script>
</html>
